home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr25
/
dualbt43.zip
/
BOOTINST.DOC
next >
Wrap
Text File
|
1993-03-04
|
13KB
|
309 lines
BOOTINST 4.3 (c) Kai Uwe Rommel
(15-Apr-1989 .. 14-Jan-1991)
READ THIS FILE ENTIRELY BEFORE USING BOOTINST !
WARNING!!! - INSTALLING SPECIAL BOOTSTRAP SOFTWARE ON A HARDDISK IS NOT
A JOB TO BE DONE BY A PC NEWCOMER BUT REQUIRES A LOT OF EXPERIENCE WITH
FORMATTING AND PARTITIONING DISKS AND WITH INSTALLING OPERATING SYSTEMS.
This program installs a new master boot program which is loaded into memory
with the partition table from the first sector of the first fixed disk of the
machine.
Every time the machine is reset, this master boot will display a menu with
all operating systems installed on the disk and ask the user to select the
system he wants to run.
The new master boot is invisible to partitioning programs like FDISK.
Partitions owned by DOS or OS/2, XENIX, UNIX, PC-IX and NOVELL are recognized
and DOS and OS/2 on a single (dual boot) partition are handled too.
a) Required steps for OS/2 1.1:
1. (if not already done)
Initialize your harddisk.
2. (may be a lot of work)
Create all partitions you want to use for DOS (and OS/2).
a) If you want to use OS/2 together with DOS 3.30 and below, now
use the DOS FDISK program to create the partitions rather than
the OS/2 FDISK because the DOS one ensures that all partitions
are 32M or smaller and that the boot partition is inside the first
32M of your disk. Format the partitions (without /S) and activate
the boot partition.
Then install OS/2 on this partitions without repartitioning and
without reformatting the disk (OS/2 should recognize the partitions
created in the above step, if you worked correctly). Install OS/2
completely until it runs without problems.
b) Otherwise, if you want to use OS/2 with DOS 4.00 and above or with
Compaq DOS 3.31, install OS/2 onto the plain disk and create the
Partitions (and format them) inside the OS/2 installation procedure.
The resulting partitions may be bigger than 32M.
3. (if additional operating systems needed)
Install all other operating systems on the rest of your disk space.
Be shure not to destroy any of the DOS and OS/2 partitions. If they
run properly, reactivate the DOS (OS/2) boot partition using FDISK.
(This step was tested only with a SCO Xenix/286 System V. Please
report problems with other OS's to me.)
4. (the MAIN step)
Boot from a DOS floppy disk. Install the dual (or multi :-) boot
by running the BOOTINST program with option -i. (The active DOS
partition still contains the OS/2 system only !)
New feature with version 4.0:
You can define a timeout period and a default operating system wich
is loaded on timeout. If you enter 0 (zero) for the timeout period,
no timeout will ever occur. If you press ENTER when asked for the
default operating system, then on timeout the operating system last
recently booted will be booted again.
BOOTINST creates two .BIN files on C:\ containing a copy of the
previous partition table sector and a copy of the C: OS/2 boot sector.
Store these two files in a safe place, you may need them in the case
of a crash.
5. (OS/2 setup correction)
(Still booted from the DOS floppy !)
Rename the OS/2 CONFIG.SYS on C: to CONFIG.OS2 and AUTOEXEC.BAT (for the
DOS mode session) to AUTOEXEC.OS2 and move COMMAND.COM (for the DOS mode
session too) into the C:\OS2 subdirectory.
Use NU (Norton Utilities) or a similar program to patch the OS2KRNL file
on C:\. Replace any occurences of CONFIG.SYS with CONFIG.OS2. Replace
AUTOEXEC.BAT strings with AUTOEXEC.OS2 in C:\OS2\COMMAND.COM too.
Correct the SHELL= line in CONFIG.OS2 to point to C:\OS2\COMMAND.COM.
This line specifies the command interpreter to be used within the DOS
mode session (be shure to include the /P switch in this line).
It should look like 'SHELL=C:\OS2\COMMAND.COM C:\OS2 /P'.
6. (DOS installation)
Now add DOS to your harddisk by simply entering 'SYS C:' from your DOS
boot disk. You may replace this DOS version by another without re-
installing the dual (or multi) boot as often as you need it by running
'SYS C:'. Copy the DOS utility programs to C:\DOS.
New feature with version 4.0:
The BOOTINST program ensures that the first two root directory slots
are free. The SYS program should not have any problems copying the two
DOS system files onto the disk. This was a problem with earlier
versions of BOOTINST prior to 4.0.
7. (DOS setup correction)
Configure your DOS by creating a CONFIG.SYS and AUTOEXEC.BAT
For clarification, patch IBMBIO.COM or IO.SYS, whatever is right for your
DOS flavour. Replace CONFIG.SYS strings with CONFIG.DOS and rename your
C:\CONFIG.SYS to CONFIG.DOS.
Move the DOS COMMAND.COM from C:\ into C:\DOS and correct or add the
SHELL= line in your CONFIG.DOS file.
It should look like 'SHELL=C:\DOS\COMMAND.COM C:\DOS /P'.
Patch the C:\DOS\COMMAND.COM to look for AUTOEXEC.DOS instead of
AUTOEXEC.BAT at boot time.
b) Required steps for OS/2 1.2 or 1.3:
1. (if not already done)
Initialize your harddisk.
2. (may be a lot of work)
Create all partitions you want to use for DOS (and OS/2).
Use DOS's FDISK to create all wanted partitions. For planned HPFS
drives, create a DOS extended partition and within this create drives
of the size of the planned HPFS partitions. Instead of formatting them
with DOS's FORMAT, use OS/2's "FORMAT /FS:HPFS" command later.
Prepare all FAT drives with DOS's FORMAT and the boot drive with
"FORMAT /S". This ensures, that all partitions have the appropriate
size for your DOS version (3.30 or 4.00 and above). Note that with the
/S option for the boot drive, the DOS system files are copied to the
special place which is needed for them (first consecutive sectors of
the partition) and thus this space is now reseved for them.
3. (OS/2 installation)
Install OS/2 now from the distibution floppies. Do NOT change the
partition setup from within the installation procedure. Choose
"Do not format ...." when you are asked to prepare the hard disk.
Test that OS/2 is running properly. You may also format then HPFS
drives with the "FORMAT /FS:HPFS x:" command.
This step overwrites the DOS boot sector with the OS/2 boot sector;
this will be corrected later. But the DOS system files are not
deleted (unlike OS/2 1.1 does) and continue to reserve the needed
space on the disk.
4. (if additional operating systems needed)
Install all other operating systems on the rest of your disk space.
Be shure not to destroy any of the DOS and OS/2 partitions. If they
run properly, reactivate the DOS (OS/2) boot partition using FDISK.
(This step was tested only with a SCO Xenix/286 System V. Please
report problems with other OS's to me.)
5. (the MAIN step)
Boot from a DOS floppy disk. Install the dual (or multi :-) boot
by running the BOOTINST program with option -i. (The active DOS
partition still contains the OS/2 system only !)
New feature with version 4.0:
You can define a timeout period and a default operating system wich
is loaded on timeout. If you enter 0 (zero) for the timeout period,
no timeout will ever occur. If you press ENTER when asked for the
default operating system, then on timeout the operating system last
recently booted will be booted again.
BOOTINST creates two .BIN files on C:\ containing a copy of the
previous partition table sector and a copy of the C: OS/2 boot sector.
The OS/2 boot sector is stored internally by BOOTINST while BOOTINST
installes itself into the partition table. Therefore, copies of the
previos versions of these sectors are written onto your disk.
Store these two files in a safe place, you may need them in the case
of a disk crash.
6. (OS/2 setup correction)
(Still booted from the DOS floppy !)
Rename the OS/2 CONFIG.SYS on C: to CONFIG.OS2 and AUTOEXEC.BAT (for the
DOS mode session) to AUTOEXEC.OS2 and move COMMAND.COM (for the DOS mode
session too) into the C:\OS2 subdirectory.
Use NU (Norton Utilities) or a similar program to patch the OS2KRNL file
on C:\. Replace any occurences of CONFIG.SYS with CONFIG.OS2. Replace
AUTOEXEC.BAT strings with AUTOEXEC.OS2 in C:\OS2\COMMAND.COM too.
Correct the SHELL= line in CONFIG.OS2 to point to C:\OS2\COMMAND.COM.
This line specifies the command interpreter to be used within the DOS
mode session (be shure to include the /P switch in this line).
It should look like 'SHELL=C:\OS2\COMMAND.COM C:\OS2 /P'.
7. (DOS installation)
Now again install DOS onto your harddisk by simply entering 'SYS C:'
from your DOS boot disk. This re-creates the DOS boot sector and
simply overwrites the DOS system files by the same files.
You may replace this DOS version by another without re-installing
the dual (or multi) boot as often as you need it by running 'SYS C:'.
Copy the DOS utility programs to C:\DOS.
8. (DOS setup correction)
Configure your DOS by creating a CONFIG.SYS and AUTOEXEC.BAT
For clarification, patch IBMBIO.COM or IO.SYS, whatever is right for your
DOS flavour. Replace CONFIG.SYS strings with CONFIG.DOS and rename your
C:\CONFIG.SYS to CONFIG.DOS.
Move the DOS COMMAND.COM from C:\ into C:\DOS and correct or add the
SHELL= line in your CONFIG.DOS file.
It should look like 'SHELL=C:\DOS\COMMAND.COM C:\DOS /P'.
Patch the C:\DOS\COMMAND.COM to look for AUTOEXEC.DOS instead of
AUTOEXEC.BAT at boot time.
If you now reboot your machine from the harddisk, you should get a prompt,
where you can select the system to boot. If DOS or OS/2 does not boot properly,
reboot from a DOS floppy disk and correct your CONFIG.xxx files or look for
mis-spellings of the CONFIG.xxx names in the patches in OS2KRNL and IBMBIO.COM.
The patch procedure for DOS and OS/2 may seem not very comfortable, but it
avoids any name conflicts at boot time. Some other dual boot programs
rename the files at boot time. This may lead into problems, when you remove
some of them (if you don't need a DOS mode session) or rename them.
If you ever have a problem, that the bootstrap program in the partition table
is overwritten by some FDISK like software (like the Xenix fdisk does sometimes)
you can reinstall the dual boot without repeating the OS/2 installation.
For this purpose use BOOTINST with option -r (new with version 4.0).
Please let me know, if you have problems using BOOTINST or if this
description of the installation procedure is too short.
This program is SHAREWARE. If you use it regularly, you are expected to
support it by reporting problems to the author and registering your copy.
Send $15, U.S. dollars, and your address to the address below (or to my bank).
If you do not want to send U.S. dollars, calculate the equivalent value
for your currency but send it only to my bank.
Kai Uwe Rommel
Zennerstrasse 1
D-8000 Muenchen 70
Western Germany
Bank: Kreissparkasse Muenchen
Bank ID 702 501 50
Account 859 488
Western Germany
You may have problems reporting problems by e-mail, because I use mail services
on our university network (Technische Universitaet Muenchen) and my mail address
may have changed and because the access to our systems from the outside world
is a little difficult.
I do not add a mail address to this file. Use the sender's address from the
original e-mail distribution file (if you got it directly from me) or send me
a letter.
THIS PROGRAM IS SHAREWARE, NOT COMMERCIAL SOFTWARE. THEREFORE I CAN NOT GIVE
ANY WARRANTY. IT IS USER-SUPPORTED SOFTWARE AND I WILL TRY TO REMOVE ANY BUGS
REPORTED TO ME BUT I CANNOT GUARANTEE THAT IT WILL WORK WITH ANY HARDWARE AND
SOFTWARE COMBINATION UNDER ALL CIRCUMSTANCES. USE IT ON YOUR OWN RISK. I WILL
NOT BE RESPONSIBLE FOR ANY DAMAGES CAUSED BY FAILURE OF THIS PROGRAM TO WORK
AS EXPECTED.
MAKE BACKUPS OF ALL YOUR SOFTWARE ON YOUR DISK(S) BEFORE INSTALLING THIS
PROGRAM BECAUSE IT IS TRICKY SYSTEM SOFTWARE.